--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Ray,
>  
> At this point we'd like to focus on getting everything 100% stable before we start adding new features.
>  
> But there is a (USR,XXXX) that you might try.  It is a way of doing a GCode callback which passes a string as a parameter.  So you should be able to use that and do whatever kind of message box you wish.   I believe it waits until motion completes and so forth before performing the callback, but otherwise you may need to do that yourself.  You should also be able to call SetAbort() before returning if the Operator doesn't wish to continue.
>  
> Regards
> TK 
>  
>
>
> ________________________________
> From: himykabibble <jagboy@...>
> To: DynoMotion@yahoogroups.com
> Sent: Monday, February 20, 2012 10:44 AM
> Subject: [DynoMotion] Re: One More PITA Enhancement Request
>
>
>  
> Brad,
>
> Perhaps, though it's not an error, it's a user message. MessageReceived might, arguably, be more appropriate, but we need to be able to tell the message originated in a (MSG,) comment, so we can display it appropriately, and allow the program to resume afterward.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> >
> > Ray,
> >
> >
> >
> > KM_Controller.ErrorReceived
> >
> >
> >
> > -Brad Murry
> >
> >
> >
> > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On
> > Behalf Of himykabibble
> > Sent: Monday, February 20, 2012 11:20 AM
> > To: DynoMotion@yahoogroups.com
> > Subject: [DynoMotion] One More PITA Enhancement Request
> >
> >
> >
> >
> >
> > Tom,
> >
> > The new (MSG, comment) functionality is a big improvement. I wonder if it
> > could be taken just one small step further, and provide an optional callback
> > to let the application display the message. The reason being.... I have my
> > handler for the PCComm MSG function, which throws up a custom dialog (not a
> > standard MessageBox) using a large enough font that I can easily read it
> > from a few feet away (which is where I normally am when running the
> > machine). The standard MessageBox font requires me to step over to the PC to
> > be able to see what it's asking for. It would also be nice to be able to map
> > the same keystroke to both the Start functionality, to dismiss the message
> > box, and to continue after an M00, rather than requiring Start for M00 and
> > Enter for the others. This would enable, for example, a pendant button to be
> > used. As it is, I need to go back and forth between the pendant and
> > keyboard/mouse during most program runs.
> >
> > Regards,
> > Ray L.
> >
>

--- In DynoMotion@yahoogroups.com, "himykabibble" <jagboy@...> wrote:
>
> Tom,
>
> I'll take a look at USR - wasn't aware of it.
>
> I wasn't suggesting this as something to do now, but as a nice to have.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Ray,
> >  
> > At this point we'd like to focus on getting everything 100% stable before we start adding new features.
> >  
> > But there is a (USR,XXXX) that you might try.  It is a way of doing a GCode callback which passes a string as a parameter.  So you should be able to use that and do whatever kind of message box you wish.   I believe it waits until motion completes and so forth before performing the callback, but otherwise you may need to do that yourself.  You should also be able to call SetAbort() before returning if the Operator doesn't wish to continue.
> >  
> > Regards
> > TK 
> >  
> >
> >
> > ________________________________
> > From: himykabibble <jagboy@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Monday, February 20, 2012 10:44 AM
> > Subject: [DynoMotion] Re: One More PITA Enhancement Request
> >
> >
> >  
> > Brad,
> >
> > Perhaps, though it's not an error, it's a user message. MessageReceived might, arguably, be more appropriate, but we need to be able to tell the message originated in a (MSG,) comment, so we can display it appropriately, and allow the program to resume afterward.
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, Brad Murry <bradodarb@> wrote:
> > >
> > > Ray,
> > >
> > >
> > >
> > > KM_Controller.ErrorReceived
> > >
> > >
> > >
> > > -Brad Murry
> > >
> > >
> > >
> > > From: DynoMotion@yahoogroups.com [mailto:DynoMotion@yahoogroups.com] On
> > > Behalf Of himykabibble
> > > Sent: Monday, February 20, 2012 11:20 AM
> > > To: DynoMotion@yahoogroups.com
> > > Subject: [DynoMotion] One More PITA Enhancement Request
> > >
> > >
> > >
> > >
> > >
> > > Tom,
> > >
> > > The new (MSG, comment) functionality is a big improvement. I wonder if it
> > > could be taken just one small step further, and provide an optional callback
> > > to let the application display the message. The reason being.... I have my
> > > handler for the PCComm MSG function, which throws up a custom dialog (not a
> > > standard MessageBox) using a large enough font that I can easily read it
> > > from a few feet away (which is where I normally am when running the
> > > machine). The standard MessageBox font requires me to step over to the PC to
> > > be able to see what it's asking for. It would also be nice to be able to map
> > > the same keystroke to both the Start functionality, to dismiss the message
> > > box, and to continue after an M00, rather than requiring Start for M00 and
> > > Enter for the others. This would enable, for example, a pendant button to be
> > > used. As it is, I need to go back and forth between the pendant and
> > > keyboard/mouse during most program runs.
> > >
> > > Regards,
> > > Ray L.
> > >
> >
>